| 1 |
<pre>Network Working Group M. St. Johns, Ed. |
| 2 |
Request for Comments: 3639 G. Huston, Ed. |
| 3 |
Category: Informational IAB |
| 4 |
October 2003 |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">Considerations on the use of a</span> |
| 8 |
<span class="h1">Service Identifier in Packet Headers</span> |
| 9 |
|
| 10 |
Status of this Memo |
| 11 |
|
| 12 |
This memo provides information for the Internet community. It does |
| 13 |
not specify an Internet standard of any kind. Distribution of this |
| 14 |
memo is unlimited. |
| 15 |
|
| 16 |
Copyright Notice |
| 17 |
|
| 18 |
Copyright (C) The Internet Society (2003). All Rights Reserved. |
| 19 |
|
| 20 |
Abstract |
| 21 |
|
| 22 |
This memo describes some considerations relating to the use of IP |
| 23 |
protocol number fields and payload protocol (e.g., TCP) port fields |
| 24 |
to identify particular services that may be associated with that port |
| 25 |
number or protocol number. |
| 26 |
|
| 27 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 28 |
|
| 29 |
This memo describes some considerations relating to the use of IP |
| 30 |
protocol number fields and payload protocol (e.g., TCP) port or |
| 31 |
service fields to identify particular services that may be associated |
| 32 |
with that port number or protocol number. It is a general statement |
| 33 |
regarding appropriate processing and use of service identifiers by |
| 34 |
intermediate systems. |
| 35 |
|
| 36 |
This memo points out that various measures by intermediate systems |
| 37 |
that are intended to filter or prevent the transmission of traffic |
| 38 |
based on the service identification within the traffic flow will have |
| 39 |
a limited effect. This will also have a major side-effect of |
| 40 |
forcing the affected services to be redesigned using various forms of |
| 41 |
encapsulation or dynamic port negotiation in order to remove the |
| 42 |
fixed service identification from the IP packet headers. The IAB |
| 43 |
does not believe this serves the general interests of the Internet |
| 44 |
community related to the design of simple and reliable Internet |
| 45 |
applications. This memo suggests some thought be given to control |
| 46 |
mechanisms that do not rely on intermediary systems taking actions |
| 47 |
based on an assumed relationship between the service identifier in |
| 48 |
the packet and the actual service of which the packet is a part. |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">St. Johns & Huston Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc3639">RFC 3639</a> Service Identifier in Packet Headers October 2003</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Service Identifiers</span> |
| 58 |
|
| 59 |
Although not necessarily by design, certain conventions have evolved |
| 60 |
with respect to the IP protocol suite relative to the identification |
| 61 |
of services within an IP traffic flow: |
| 62 |
|
| 63 |
o Within the IP protocol suite, end point identifiers (e.g., |
| 64 |
TCP/UDP/SCTP port numbers, IP protocol numbers) are designed to |
| 65 |
identify services to end points. In particular, TCP, UDP or SCTP |
| 66 |
(Stream Control Transmission Protocol) port numbers are intended |
| 67 |
to identify the source service location and the destination |
| 68 |
service entity to the destination end point. |
| 69 |
|
| 70 |
o The IP [<a href="#ref-2" title=""Internet Protocol"">2</a>] datagram header contains the source and destination |
| 71 |
address of the datagram as well as an indication of the upper- |
| 72 |
level protocol (ULP) carried within the datagram. If the ULP is |
| 73 |
either TCP [<a href="#ref-3" title=""Transmission Control Protocol"">3</a>], UDP [<a href="#ref-1" title=""User Datagram Protocol"">1</a>], or SCTP [<a href="#ref-8" title=""Stream Control Transmission Protocol"">8</a>] the payload will contain both |
| 74 |
source and destination port numbers which allows differentiation |
| 75 |
between services (e.g., TELNET, HTTP) and between multiple |
| 76 |
instances of the same service between the pair of hosts described |
| 77 |
by the source and destination address. |
| 78 |
|
| 79 |
o By convention, for at least TCP and UDP, certain port numbers are |
| 80 |
used as rendezvous points and are considered "well known" on the |
| 81 |
source or destination side of the communication. Such rendezvous |
| 82 |
points are maintained in an IANA registry currently located at |
| 83 |
[<a href="#ref-11" title=""IANA Protocol Numbers and Assignment Services"">11</a>]. Specific registries for protocol and port numbers are at |
| 84 |
[<a href="#ref-12" title=""IANA Protocol Number Registry"">12</a>] and [<a href="#ref-13" title=""IANA Port Number Registry"">13</a>]. |
| 85 |
|
| 86 |
o Notwithstanding the "well knownness" of any given port, port |
| 87 |
numbers are only guaranteed to be meaningful to the end systems. |
| 88 |
An intermediate system should generally not impute specific |
| 89 |
meaning to any given port number, unless specifically indicated by |
| 90 |
an end system (e.g., via the Resource Reservation Protocol (RSVP) |
| 91 |
[<a href="#ref-4" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">4</a>]) or agreed to by convention among the end systems and one or |
| 92 |
more specific intermediate systems (e.g., firewall traversal for |
| 93 |
the IP Security Protocol (IPSEC) [<a href="#ref-5" title=""Security Architecture for the Internet Protocol"">5</a>]). |
| 94 |
|
| 95 |
o Some services make use of protocol interactions to dynamically |
| 96 |
allocate service identifiers (i.e., port numbers) to specific |
| 97 |
communications. One specific example of this is the Session |
| 98 |
Initiation Protocol (SIP) [<a href="#ref-9" title=""SIP: Session Initiation Protocol"">9</a>]. The implication of this is that |
| 99 |
intermediate systems cannot relate the service identifiers to the |
| 100 |
actual service unless they participate in the protocols which |
| 101 |
allocate the service identifiers, or are explicitly notified of |
| 102 |
the outcome of the allocation. |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">St. Johns & Huston Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc3639">RFC 3639</a> Service Identifier in Packet Headers October 2003</span> |
| 111 |
|
| 112 |
|
| 113 |
o Various products and service-related mechanisms deployed today |
| 114 |
take advantage of the fact that some service identifiers are |
| 115 |
relatively stable (and well known) to do various things (e.g., |
| 116 |
firewall filtering, QOS marking). |
| 117 |
|
| 118 |
o Certain network operations, such as various forms of packet |
| 119 |
encapsulation (e.g., tunneling) and encryption, can occlude this |
| 120 |
port number (or service identifier) while an IP packet is in |
| 121 |
transit within the network. For example, both the IPSEC |
| 122 |
Encapsulating Security Payload (ESP) [<a href="#ref-6" title=""IP Encapsulating Security Payload (ESP)"">6</a>] and Generic Routing |
| 123 |
Encapsulation (GRE) [<a href="#ref-7" title=""Generic Routing Encapsulation (GRE)"">7</a>] both provide means for tunneling an IP |
| 124 |
datagram within another IP datagram. The service information |
| 125 |
becomes obscured and, in some instances, encrypted. |
| 126 |
|
| 127 |
o Cooperating end systems may elect to use arbitrarily selected port |
| 128 |
numbers for any service. The port numbers used in such cases may |
| 129 |
be statically defined, through coordinated configuration of the |
| 130 |
cooperating end systems through use of a common application or |
| 131 |
operating system, or by dynamic selection as an outcome of a |
| 132 |
rendezvous protocol. |
| 133 |
|
| 134 |
Intermediate system imposed service-based controls may block |
| 135 |
legitimate uses by subscribers. For example, some service providers |
| 136 |
are blocking port 25 (i.e., notionally SMTP) traffic for the stated |
| 137 |
purpose of trying to prevent SPAM, but which can also block |
| 138 |
legitimate email to the end user. |
| 139 |
|
| 140 |
Attempts by intermediate systems to impose service-based controls on |
| 141 |
communications against the perceived interests of the end parties to |
| 142 |
the communication are often circumvented [<a href="#ref-10" title=""STUDENTS EVADE UNIVERSITY TACTICS TO PROTECT MEDIA FILES"">10</a>]. Services may be |
| 143 |
tunneled within other services, proxied by a collaborating external |
| 144 |
host (e.g., an anonymous redirector), or simply run over an alternate |
| 145 |
port (e.g., port 8080 vs port 80 for HTTP). Another means of |
| 146 |
circumvention is alteration of the service behavior to use a dynamic |
| 147 |
port negotiation phase, in order to avoid use of a constant port |
| 148 |
address. |
| 149 |
|
| 150 |
For the purposes of this memo, a "party to a communication" is either |
| 151 |
the sender, receiver, or an authorized agent of the sender or |
| 152 |
receiver in the path. |
| 153 |
|
| 154 |
If intermediate systems take actions on behalf of one or more parties |
| 155 |
to the communication or affecting the communication, a good rule of |
| 156 |
thumb is they should only take actions that are beneficial to or |
| 157 |
approved by one or more of the parties, within the operational |
| 158 |
parameters of the service-specific protocol, or otherwise unlikely to |
| 159 |
lead to widespread evasion by the user community. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">St. Johns & Huston Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc3639">RFC 3639</a> Service Identifier in Packet Headers October 2003</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Ramifications</span> |
| 170 |
|
| 171 |
The IAB observes that having stable and globally meaningful service |
| 172 |
identifiers visible at points other than the end systems can be |
| 173 |
useful for the purposes of determining network behavior and network |
| 174 |
loading on a macro level. The IAB also observes that application |
| 175 |
protocols that include dynamic port negotiation for both ends of a |
| 176 |
connection tend to add to the complexity of the applications. |
| 177 |
|
| 178 |
Dynamic port negotiation for a protocol may also limit or prohibit |
| 179 |
its use in situations where the service provider (e.g., ISP or |
| 180 |
employer) has instituted some form of service filtering through port |
| 181 |
blocking mechanisms. |
| 182 |
|
| 183 |
From this perspective of network and application utility, it is |
| 184 |
preferable that no action or activity be undertaken by any agency, |
| 185 |
carrier, service provider, or organization which would cause end- |
| 186 |
users and protocol designers to generally obscure service |
| 187 |
identification information from the IP packet header. |
| 188 |
|
| 189 |
Nothing in this statement should be construed as opposing |
| 190 |
encapsulation, application security, end-to-end encryption, or other |
| 191 |
processes beneficial or specifically desired by the end-users. |
| 192 |
|
| 193 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 194 |
|
| 195 |
This document is a general statement regarding appropriate processing |
| 196 |
and use of service identifiers by intermediate systems. If enough |
| 197 |
agencies, carriers, service providers, and organizations ignore the |
| 198 |
concerns voiced here, the utility of port and protocol numbers, |
| 199 |
general network analysis, end-user beneficial filtering (e.g., |
| 200 |
preventing DDOS attacks), and other common uses of these service |
| 201 |
identifiers might be adversely affected. |
| 202 |
|
| 203 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span> |
| 204 |
|
| 205 |
[<a id="ref-1">1</a>] Postel, J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>, August |
| 206 |
1980. |
| 207 |
|
| 208 |
[<a id="ref-2">2</a>] Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>, September |
| 209 |
1981. |
| 210 |
|
| 211 |
[<a id="ref-3">3</a>] Postel, J., "Transmission Control Protocol", STD 7, <a href="./rfc793">RFC 793</a>, |
| 212 |
September 1981. |
| 213 |
|
| 214 |
[<a id="ref-4">4</a>] Braden, B., Ed., Zhang, L., Berson, S., Herzog, S. and S. |
| 215 |
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 |
| 216 |
Functional Specification", <a href="./rfc2205">RFC 2205</a>, September 1997. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">St. Johns & Huston Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc3639">RFC 3639</a> Service Identifier in Packet Headers October 2003</span> |
| 223 |
|
| 224 |
|
| 225 |
[<a id="ref-5">5</a>] Kent, S. and R. Atkinson, "Security Architecture for the |
| 226 |
Internet Protocol", <a href="./rfc2401">RFC 2401</a>, November 1998. |
| 227 |
|
| 228 |
[<a id="ref-6">6</a>] Kent, S. and R. Atkinson, "IP Encapsulating Security Payload |
| 229 |
(ESP)", <a href="./rfc2406">RFC 2406</a>, November 1998. |
| 230 |
|
| 231 |
[<a id="ref-7">7</a>] Farinacci, D., Li, T., Hanks, S., Meyer, D. and P. Traina, |
| 232 |
"Generic Routing Encapsulation (GRE)", <a href="./rfc2784">RFC 2784</a>, March 2000. |
| 233 |
|
| 234 |
[<a id="ref-8">8</a>] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, |
| 235 |
H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson, |
| 236 |
"Stream Control Transmission Protocol", <a href="./rfc2960">RFC 2960</a>, October 2000. |
| 237 |
|
| 238 |
[<a id="ref-9">9</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., |
| 239 |
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: |
| 240 |
Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, June 2002. |
| 241 |
|
| 242 |
[<a id="ref-10">10</a>] New York Times, "STUDENTS EVADE UNIVERSITY TACTICS TO PROTECT |
| 243 |
MEDIA FILES", 27th November 2002. |
| 244 |
|
| 245 |
[<a id="ref-11">11</a>] IANA, "IANA Protocol Numbers and Assignment Services", May |
| 246 |
2003, <<a href="http://www.iana.org/numbers.htm">http://www.iana.org/numbers.htm</a>>. |
| 247 |
|
| 248 |
[<a id="ref-12">12</a>] IANA, "IANA Protocol Number Registry", May 2003, <<a href="http://www.iana.org/assignments/protocol-numbers">http://</a> |
| 249 |
<a href="http://www.iana.org/assignments/protocol-numbers">www.iana.org/assignments/protocol-numbers</a>>. |
| 250 |
|
| 251 |
[<a id="ref-13">13</a>] IANA, "IANA Port Number Registry", May 2003, <<a href="http://www.iana.org/assignments/port-numbers">http://</a> |
| 252 |
<a href="http://www.iana.org/assignments/port-numbers">www.iana.org/assignments/port-numbers</a>>. |
| 253 |
|
| 254 |
|
| 255 |
|
| 256 |
|
| 257 |
|
| 258 |
|
| 259 |
|
| 260 |
|
| 261 |
|
| 262 |
|
| 263 |
|
| 264 |
|
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">St. Johns & Huston Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc3639">RFC 3639</a> Service Identifier in Packet Headers October 2003</span> |
| 279 |
|
| 280 |
|
| 281 |
Intellectual Property Statement |
| 282 |
|
| 283 |
The IETF takes no position regarding the validity or scope of any |
| 284 |
intellectual property or other rights that might be claimed to |
| 285 |
pertain to the implementation or use of the technology described in |
| 286 |
this document or the extent to which any license under such rights |
| 287 |
might or might not be available; neither does it represent that it |
| 288 |
has made any effort to identify any such rights. Information on the |
| 289 |
IETF's procedures with respect to rights in standards-track and |
| 290 |
standards-related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of |
| 291 |
claims of rights made available for publication and any assurances of |
| 292 |
licenses to be made available, or the result of an attempt made to |
| 293 |
obtain a general license or permission for the use of such |
| 294 |
proprietary rights by implementors or users of this specification can |
| 295 |
be obtained from the IETF Secretariat. |
| 296 |
|
| 297 |
The IETF invites any interested party to bring to its attention any |
| 298 |
copyrights, patents or patent applications, or other proprietary |
| 299 |
rights which may cover technology that may be required to practice |
| 300 |
this standard. Please address the information to the IETF Executive |
| 301 |
Director. |
| 302 |
|
| 303 |
|
| 304 |
|
| 305 |
|
| 306 |
|
| 307 |
|
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">St. Johns & Huston Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc3639">RFC 3639</a> Service Identifier in Packet Headers October 2003</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. IAB Members</span> |
| 338 |
|
| 339 |
Internet Architecture Board Members at the time this document was |
| 340 |
completed were: |
| 341 |
|
| 342 |
Bernard Aboba |
| 343 |
Harald Alvestrand |
| 344 |
Rob Austein |
| 345 |
Leslie Daigle, Chair |
| 346 |
Patrik Faltstrom |
| 347 |
Sally Floyd |
| 348 |
Jun-ichiro Itojun Hagino |
| 349 |
Mark Handley |
| 350 |
Geoff Huston |
| 351 |
Charlie Kaufman |
| 352 |
James Kempf |
| 353 |
Eric Rescorla |
| 354 |
Michael St Johns |
| 355 |
|
| 356 |
Editors' Addresses |
| 357 |
|
| 358 |
Mike St Johns |
| 359 |
Internet Architecture Board |
| 360 |
|
| 361 |
EMail: [email protected] |
| 362 |
|
| 363 |
|
| 364 |
Geoff Huston |
| 365 |
Internet Architecture Board |
| 366 |
|
| 367 |
EMail: [email protected] |
| 368 |
|
| 369 |
|
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">St. Johns & Huston Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc3639">RFC 3639</a> Service Identifier in Packet Headers October 2003</span> |
| 391 |
|
| 392 |
|
| 393 |
Full Copyright Statement |
| 394 |
|
| 395 |
Copyright (C) The Internet Society (2003). All Rights Reserved. |
| 396 |
|
| 397 |
This document and translations of it may be copied and furnished to |
| 398 |
others, and derivative works that comment on or otherwise explain it |
| 399 |
or assist in its implementation may be prepared, copied, published |
| 400 |
and distributed, in whole or in part, without restriction of any |
| 401 |
kind, provided that the above copyright notice and this paragraph are |
| 402 |
included on all such copies and derivative works. However, this |
| 403 |
document itself may not be modified in any way, such as by removing |
| 404 |
the copyright notice or references to the Internet Society or other |
| 405 |
Internet organizations, except as needed for the purpose of |
| 406 |
developing Internet standards in which case the procedures for |
| 407 |
copyrights defined in the Internet Standards process must be |
| 408 |
followed, or as required to translate it into languages other than |
| 409 |
English. |
| 410 |
|
| 411 |
The limited permissions granted above are perpetual and will not be |
| 412 |
revoked by the Internet Society or its successors or assignees. |
| 413 |
|
| 414 |
This document and the information contained herein is provided on an |
| 415 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 416 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 417 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 418 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 419 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 420 |
|
| 421 |
Acknowledgement |
| 422 |
|
| 423 |
Funding for the RFC Editor function is currently provided by the |
| 424 |
Internet Society. |
| 425 |
|
| 426 |
|
| 427 |
|
| 428 |
|
| 429 |
|
| 430 |
|
| 431 |
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
St. Johns & Huston Informational [Page 8] |
| 445 |
</pre> |