idnits 2.17.1 draft-kuehlewind-system-ports-00.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 (August 15, 2017) is 2443 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) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 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 ETH Zurich 4 Intended status: Standards Track August 15, 2017 5 Expires: February 16, 2018 7 Reassignment of System Ports to the IESG 8 draft-kuehlewind-system-ports-00 10 Abstract 12 This document reassigns all System Ports to the IESG that have been 13 assigned to individuals prior to the publication of RFC6335. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on February 16, 2018. 32 Copyright Notice 34 Copyright (c) 2017 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 1. Introduction 49 RFC 6335 [RFC6335] requires System Ports, also known as the Well 50 Known Ports, in the range from 0 to 1023, to be assigned by the "IETF 51 Review" or "IESG Approval" procedures [RFC5226]. Further, for 52 assignments done through RFCs published via the "IETF Document 53 Stream" [RFC4844], the Assignee will be the IESG with the IETF Chair 54 as the Contact. Therefore, all System Ports must be assigned to the 55 IESG. 57 However, ports that were assigned before the publication of RFC 6335, 58 are often assigned to individuals, even if they are part of the 59 System Port range. Besides the fact that System Ports that are 60 widely used by IETF protocols under IETF change control, this is 61 especially problematic if the assignment is or should be changed. 62 The Assignee, can change the assignment without confirmation of the 63 IETF. However, if the IETF process requires a change, including 64 deassignment, this cannot be done without the agreement of the 65 original Assignee. Furthermore, no procedure is defined to change 66 the assignment in cases where the original Assignee is not reachable 67 or for any other reason not available anymore, 69 This document instructs IANA to re-assign all currently assigned 70 System Ports in the range from 0 to 1023 to the IESG, thus aligning 71 existing entries in the "Service Name and Transport Protocol Port 72 Number Registry" with the current procedures defined in RFC 6335. 74 2. IANA Considerations 76 IANA [will re-assign/has reassigned] all System Ports in the port 77 range from 0 to 1023 that are currently assigned in the "Service Name 78 and Transport Protocol Port Number Registry" to the IESG 79 as Asignee and the IETF Chair as 80 Contact. 82 IANA should inform the current Assignees by email with the registered 83 email address about this change. However, IANA does not need to take 84 any actions to inform the current Assignee if the provided email 85 address in not valid anymore, or the Assignee is not reachable 86 anymore with the provided email address. 88 As part of this change IANA [will also upadte/has further updated] 89 the Reference column with the following reference for the listed 90 ports that have a corresponding published RFC that uses this port 91 number, as well as the Assignment Notes column for historic RFCs: 93 +-----------+----------+--------------+-------------+---------------+ 94 | Service | Port | Transport | Reference | Assignment | 95 | Name | Number | protocol | | Notes | 96 +-----------+----------+--------------+-------------+---------------+ 97 | systat | 11 | tcp | RFC866 | | 98 | systat | 11 | udp | RFC866 | | 99 | qotd | 17 | tcp | RFC865 | | 100 | qotd | 17 | upd | RFC865 | | 101 | msp | 18 | tcp | RFC1312 | | 102 | msp | 18 | udp | RFC1312 | | 103 | chargen | 19 | tcp | RFC864 | | 104 | chargen | 19 | udp | RFC864 | | 105 | smtp | 25 | tcp | RFC5321 | | 106 | smtp | 25 | udp | RFC5321 | | 107 | time | 37 | tcp | RFC868 | | 108 | time | 37 | udp | RFC868 | | 109 | rap | 38 | tcp | RFC1476 | | 110 | rap | 38 | udp | RFC1476 | | 111 | rlp | 39 | tcp | RFC887 | | 112 | rlp | 39 | udp | RFC887 | | 113 | nicname | 43 | tcp | RFC3912 | | 114 | nicname | 43 | udp | RFC3912 | | 115 | tacacs | 49 | tcp | RFC1492 | | 116 | tacacs | 49 | udp | RFC1492 | | 117 | domain | 53 | tcp | RFC1035 | | 118 | domain | 53 | udp | RFC1035 | | 119 | whoispp | 63 | tcp | RFC1913 | | 120 | whoispp | 63 | udp | RFC1913 | | 121 | bootps | 67 | tcp | RFC2131 | | 122 | bootps | 67 | udp | RFC2131 | | 123 | bootpc | 68 | tcp | RFC2131 | | 124 | bootpc | 68 | udp | RFC2131 | | 125 | tftp | 69 | tcp | RFC1350 | | 126 | tftp | 69 | udp | RFC1350 | | 127 | gopher | 70 | tcp | RFC1436 | | 128 | gopher | 70 | udp | RFC1436 | | 129 | finger | 79 | tcp | RFC1288 | | 130 | finger | 79 | udp | RFC1288 | | 131 | www-http | 80 | tcp | RFC7230, | | 132 | | | | RFC7540 | | 133 | www-http | 80 | udp | RFC7230, | | 134 | | | | RFC7540 | | 135 | kerberos | 88 | tcp | RFC4120 | | 136 | kerberos | 88 | udp | RFC4120 | | 137 | dixie | 96 | tcp | RFC1249 | | 138 | dixie | 96 | udp | RFC1249 | | 139 | hostname | 101 | tcp | RFC953 | This RFC is | 140 | | | | | historic. | 141 | hostname | 101 | udp | RFC953 | This RFC is | 142 | | | | | historic. | 143 | cso | 105 | tcp | RFC2378 | | 144 | cso | 105 | udp | RFC2378 | | 145 | rtelnet | 107 | tcp | RFC818 | This RFC is | 146 | | | | | historic. | 147 | rtelnet | 107 | udp | RFC818 | This RFC is | 148 | | | | | historic. | 149 | sunrpc | 111 | tcp | RFC1833 | | 150 | sunrpc | 111 | udp | RFC1833 | | 151 | auth | 113 | tcp | RFC1413 | | 152 | auth | 113 | udp | RFC1413 | | 153 | sftp | 115 | tcp | RFC913 | This RFC is | 154 | | | | | historic. | 155 | sftp | 115 | udp | RFC913 | This RFC is | 156 | | | | | historic. | 157 | cfdptkt | 120 | tcp | RFC1235 | | 158 | cfdptkt | 120 | udp | RFC1235 | | 159 | pwdgen | 129 | tcp | RFC972 | | 160 | pwdgen | 129 | udp | RFC972 | | 161 | imap | 143 | tcp | RFC3501 | | 162 | imap | 143 | udp | RFC3501 | | 163 | bftp | 152 | tcp | RFC1068 | | 164 | bftp | 152 | udp | RFC1068 | | 165 | sgmp | 153 | tcp | RFC1028 | This RFC is | 166 | | | | | historic. | 167 | sgmp | 153 | udp | RFC1028 | This RFC is | 168 | | | | | historic. | 169 | snmp | 161 | tcp | RFC3430 | | 170 | snmp | 161 | udp | RFC3417 | | 171 | snmptrap | 162 | tcp | RFC3430 | | 172 | snmptrap | 162 | udp | RFC3417 | | 173 | bgp | 179 | tcp | RFC4271 | | 174 | bgp | 179 | udp | RFC4271 | | 175 | irc | 194 | tcp | RFC1459 | | 176 | irc | 194 | udp | RFC1459 | | 177 | smux | 199 | tcp | RFC1227 | This RFC is | 178 | | | | | historic. | 179 | smux | 199 | udp | RFC1227 | This RFC is | 180 | | | | | historic. | 181 | ipx | 213 | tcp | RFC1234 | This RFC is | 182 | | | | | historic. | 183 | ipx | 213 | upd | RFC1234 | This RFC is | 184 | | | | | historic. | 185 | mpp | 218 | tcp | RFC1204 | | 186 | mpp | 218 | udp | RFC1204 | | 187 | bgmp | 264 | tcp | RFC3913 | This RFC is | 188 | | | | | historic. | 189 | bgmp | 264 | udp | RFC3913 | This RFC is | 190 | | | | | historic. | 191 | pt-tls | 271 | tcp | RFC6876 | | 192 | pt-tls | 271 | udp | RFC6876 | | 193 | rtsps | 322 | tcp | RFC7826 | | 194 | rtsps | 322 | udp | RFC7826 | | 195 | odmr | 366 | tcp | RFC2645 | | 196 | odmr | 366 | udp | RFC2645 | | 197 | aurp | 387 | tcp | RFC1504 | | 198 | aurp | 387 | udp | RFC1504 | | 199 | ldap | 389 | tcp | RFC4516 | | 200 | ldap | 389 | udp | RFC4516 | | 201 | svrloc | 427 | tcp | RFC2608 | | 202 | svrloc | 427 | udp | RFC2608 | | 203 | https | 443 | tcp | RFC7230, | | 204 | | | | RFC7540 | | 205 | https | 443 | udp | RFC7230, | | 206 | | | | RFC7540 | | 207 | kpasswd | 464 | tcp | RFC3244 | | 208 | kpasswd | 464 | udp | RFC3244 | | 209 | photuris | 468 | tcp | RFC2522 | | 210 | photuris | 468 | udp | RFC2522 | | 211 | isakmp | 500 | tcp | RFC7296 | | 212 | isakmp | 500 | udp | RFC7296 | | 213 | syslog | 514 | tcp | RFC5426 | | 214 | syslog | 514 | udp | RFC5426 | | 215 | printer | 515 | tcp | RFC1179 | | 216 | printer | 515 | udp | RFC1179 | | 217 | router | 520 | tcp | RFC2453 | | 218 | router | 520 | udp | RFC2453 | | 219 | ripng | 521 | tcp | RFC2080 | | 220 | ripng | 521 | udp | RFC2080 | | 221 | rtsp | 554 | tcp | RFC7826 | | 222 | rtsp | 554 | udp | RFC7826 | | 223 | vemmi | 575 | tcp | RFC2122 | | 224 | vemmi | 575 | udp | RFC2122 | | 225 | ipp | 631 | tcp | RFC8010 | | 226 | ipp | 631 | udp | RFC8010 | | 227 | msdp | 639 | tcp | RFC3618 | | 228 | msdp | 639 | udp | RFC3618 | | 229 | ldp | 646 | tcp | RFC3036 | | 230 | ldp | 646 | udp | RFC3036 | | 231 | rrp | 648 | tcp | RFC2832 | | 232 | rrp | 648 | udp | RFC2832 | | 233 | aodv | 654 | tcp | RFC3561 | | 234 | aodv | 654 | udp | RFC3561 | | 235 | acap | 674 | tcp | RFC2244 | | 236 | acap | 674 | udp | RFC2244 | | 237 | olsr | 698 | tcp | RFC3626 | | 238 | olsr | 698 | udp | RFC3626 | | 239 | agentx | 705 | tcp | RFC2741 | | 240 | agentx | 705 | udp | RFC2741 | | 241 +-----------+----------+--------------+-------------+---------------+ 243 As part of this maintance effort, IANA [will further added/has 244 further added] the following entry with the IESG as Assignee and the 245 IETF chair as Contact: 247 +--------------+-------------+--------------------+-----------+ 248 | Service Name | Port Number | Transport protocol | Reference | 249 +--------------+-------------+--------------------+-----------+ 250 | rmt | 411 | tcp | RFC1202 | 251 +--------------+-------------+--------------------+-----------+ 253 3. Security Considerations 255 [RFC-Editor please remove this section before publication.] 257 This draft has no security consideration. 259 4. References 261 4.1. Normative References 263 [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. 264 Cheshire, "Internet Assigned Numbers Authority (IANA) 265 Procedures for the Management of the Service Name and 266 Transport Protocol Port Number Registry", BCP 165, 267 RFC 6335, DOI 10.17487/RFC6335, August 2011, 268 . 270 4.2. Informative References 272 [RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC 273 Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844, 274 July 2007, . 276 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 277 IANA Considerations Section in RFCs", RFC 5226, 278 DOI 10.17487/RFC5226, May 2008, 279 . 281 Author's Address 283 Mirja Kuehlewind (editor) 284 ETH Zurich 286 Email: ietf@kuehlewind.net